This repository has been archived by the owner on Feb 21, 2023. It is now read-only.
Cleanup of REST API #44
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
letmaik
commented
Feb 14, 2023
letmaik
commented
Feb 14, 2023
letmaik
commented
Feb 14, 2023
…rom entry resource
text mostly from RFC9162
Co-authored-by: Thomas Fossati <tho.ietf@gmail.com>
|
I addressed all feedback that came in and will move this PR over to the repo in ietf-wg-scitt. More review can happen there. I accidently opened this PR here in the old repo. |
|
thanks @letmaik |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's not clear yet whether and in what form a REST API will be standardized but this PR cleans up the existing section and makes the API vendor-neutral (previously, some CCF-specific bits had leaked into it) including allowing for registration of claims to be a long-running operation which provides more flexibility for implementations.